Computing device display management

ABSTRACT

The description relates to computing devices that have one or more displays. One example can manage the display as a unit and identify a change in a condition associated with the display. The example can alter at least one of a location, aspect ratio, or size of the unit based on the condition.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings illustrate implementations of the conceptsconveyed in the present document. Features of the illustratedimplementations can be more readily understood by reference to thefollowing description taken in conjunction with the accompanyingdrawings. Like reference numbers in the various drawings are usedwherever feasible to indicate like elements. Further, the left-mostnumeral of each reference number conveys the FIG. and associateddiscussion where the reference number is first introduced. Where spacepermits, elements and their associated reference numbers are both shownon the drawing page for the reader's convenience. Otherwise, only thereference numbers are shown.

FIGS. 1A-3D show perspective views of example computing devices andassociated input devices in accordance with some implementations of thepresent display management concepts.

FIGS. 4 and 5 are example computing device display management blockdiagrams in accordance with some implementations of the present displaymanagement concepts.

FIG. 6 is an example computing device display management flowchart inaccordance with some implementations of the present concepts.

DESCRIPTION

The present concepts relate to devices, such as computing devices andassociated input devices. The computing device can include one or moredisplays. The displays can be managed as one or more units. The units ofthe displays can be managed for a specific functionality. For instance,one unit can be used to present content as a graphical user interfaces(GUIs) while another unit is used to present other content as anotherGUI and still another unit can be used as an input device (e.g., theunit may function as a trackpad). The overall portion of the displaydedicated to each unit and/or the location of the unit can be varieddepending upon various conditions. For instance, in some cases, someunits may be blocked from view. For example, a user may place the inputdevice on the display. Units affected by the blockage can bereconfigured (e.g., their size and/or location on the display can bechanged) to accommodate the blockage. The unit underlying the inputdevice may be managed in a manner that reflects that it is not visibleto the user.

Sometimes users can be disoriented or confused by sudden reconfigurationof the units. As such, the present concepts can provide visualindications to the user that indicate how the units are going to bereconfigured (e.g., before the input device is physically positioned onthe display). The visual indications may be accomplished with one ormore transition GUIs that reflect unit size and/or location on thedisplay so that the user can understand what is happening. Further, thepresence of the input device may make some units unsuitable for theirpresent use. In such cases, the present concepts can assign analternative functionality to those units. These aspects and others aredescribed in more detail below.

Introductory FIGS. 1A-1F shows a system 100 that can include an examplecomputing device 102 and an associated input device 104 that cancommunicate with computing device 102. In this example, the associatedinput device 104 is a wireless detachable input device that cancommunicate with computing device 102 via one or more wirelesstechnologies, such as Bluetooth, and/or near field communication (NFC),among others. In this case, the computing device 102 has first andsecond portions 106 and 108 that are rotatably secured together by ahinge assembly 110. Other example computing devices could be manifest asa single portion (e.g., a tablet) or more than two portions. Exampleinput devices 104 can include a keyboard, a touch pad, and/or a gamecontroller, among others.

Displays 112 can be positioned on the first and/or second portions 106and 108. Displays often are touch sensitive displays that can detectpressure and/or proximity of nearby objects. Display 112(1) can extendfrom a hinge end 114 to a distal end 116 to define a length L₁ and canalso define a width W₁ that lies orthogonal to the length L₁. Display112(2) can extend from a hinge end 118 to a distal end 120 to define alength L₂ and can also define a width W₂ that lies orthogonal to thelength L₂. The length and the width can define the display area (e.g.,rectangle) of the display. Input device 104 can have a width W₃ thatlies orthogonal to the length L₃. In the illustrated case, the width ofthe input device is approximately the same as the width of the displays.In other cases, the input device could be narrower or wider than thedisplays.

System 100 can also include sensors 122 that can convey informationabout the position and/or movement of input device 104 relative tocomputing device 102. In this example, sensors 122(1) and 122(2) arepositioned on computing device 102 and sensors 122(3) and 122(4) arepositioned on input device 104. In one implementation, the sensors canbe manifest as near field communication (NFC) sensors. NFC sensors canutilize electromagnetic induction between two loop antennas tocommunicate data between two devices. However, the present concepts canleverage changes to the electromagnetic fields to convey informationabout the position and/or movement of the input device 104 relative tothe computing device 102. This technique can be effective out to around10-30 centimeters, for example. Alternatively, Bluetooth sensors (e.g.,Bluetooth Low Energy (BLE)) beacons can be employed to track thelocation and/or movement of the input device relative to the computingdevice. Further, as mentioned above, the displays can have pressureand/or proximity sensors that can contribute position and/or movementinformation.

In this configuration, units 124 of displays 112 (e.g., of the displayarea) can be managed for specific functions. In FIG. 1A, unit 124(1)includes all of display 112(1) and unit 124(2) includes all of display112(2). This relationship between the units and the displays can befluid as will become apparent through the description below (e.g., thesize, location, and/or number of units can change).

For purposes of explanation, assume that unit 124(1) is being utilizedto present a first graphical user interface (GUI) 126(1) and unit 124(2)is being utilized to present a second GUI 126(2). For instance, thefirst GUI might be associated with a first application and the secondGUI might be associated with a second application.

FIGS. 1A-1F capture specific instances of a process that may extend fora time duration. From one perspective, the instances captured in theseries of FIGS. 1A-1F may be viewed as snapshots from a videoprogression from a time starting at FIG. 1A (e.g., originalconfiguration and culminating at FIG. 1F (e.g., updated configuration)).Starting with FIG. 1A, the input device 104 is physically separated fromthe computing device 102. The user can utilize the input device tocontrol the computing device, such as the GUIs 126. For instance, GUI126A(1) could be associated with a first application and GUI 126A(2)could be associated with a second application. Now assume that the userdecides to move the input device 104 and place it on the computingdevice's second portion 108.

FIG. 1B shows user 128 moving the input device 104 toward the computingdevice 102 (in this case toward the second portion 108). This movement,such as location and direction of movement, has been detected by thesensors 122. Computing device 102 can predict that the movement willresult in the input device 104 positioned on and occluding a portion ofthe second display 112(2). As such, units on this display can be moved,such as to first display 112(1). However, instantaneous reconfigurationof the units may disorient the user. Thus, GUIs 126B(1) and 126B(2) canbe termed transition GUIs, which show an intervening configuration ofthe units 124B from the initial configuration (FIG. 1A) to the updatedconfiguration of reconfigured units 124E of FIG. 1F.

FIG. 1B shows the initial transition GUIs 126B(1) and 1266(2).Transition GUI 126B(1) is moving to the left and GUI 126B(2) is movingto the right. At this point, each transition GUI 126B occupies a portionof the first display 112(1) and the second display 112(2). Here,transition GUI 126B(1) occupies a majority of first display 112(1) buthas moved to the left to create a space for transition GUI 1266(2).Similarly, transition GUI 126B(2) has moved to the right on seconddisplay 112(2) where it still occupies a majority of the space and italso occupies the rightmost portion of first display 112(1). In thiscase, subsequent transition GUIs are shown in FIGS. 1C-1D. Thetransition GUIs can provide a visual indication to the user thatexplains how the units are being reconfigured due to the predictedchanging conditions (e.g., changing position of the input device).

To summarize in this example scenario starting at FIG. 1A, unit 124(1)occupies all of the first display 112(1) and unit 124(2) occupies all ofsecond display 112(2) (e.g., the units are vertically arranged one atopthe other). Eventually, in FIG. 1E the first unit 124(1) and the secondunit 124(2) are both on first display 112(1) in a side-by-side (e.g.,horizontal relationship). FIGS. 1B-1D show the visual indictors that arepresented to help the reader understand what is happening.

FIG. 1C shows a subsequent view where the user is continuing to move theinput device 104 toward the computing device 102. At this pointtransition GUIs 126C are positioned side-by-side on both displays 112.The transition GUIs 126C are positioned on the first display 112(1) andextend down onto second display 112(2).

FIG. 1D shows a subsequent point where the input device 104 is partlyover the second display 112(2). The presence of the input device (e.g.,sensed position) can be sensed by sensors 122 and/or by sensors ofdisplay 112(2) (e.g., in the case where the display is a touch sensitivedisplay). Transition GUIs 126D(1) and 126D(2) have moved away from theinput device 104 and an additional transition GUI 126D(3) indicates athird unit 124D(3) and additional transition GUI indicates a fourth unit124D(4) on the second display 112(2). The third unit 124D(3) can be usedfor various functions, such as a touch sensitive tool bar, or a touchpad, among others. The fourth unit 124D(4) can be an area blocked by theinput device and thus not used to present content or for receiving touchgestures (e.g., no corresponding GUI). In some implementations, theblocked fourth unit 124D(4) can be powered down (e.g., operated in alower power state) to reduce resource usage (e.g., battery usage). Forinstance, the occluded fourth unit 124D(4) of the display could bepowered down by turning off pixels in the case where the display is anOLED display, or turning off certain LEDs for an LCD display, amongothers.

FIG. 1E shows a subsequent point where the input device 104 ispositioned on the second display 112(2). Thus, fourth unit 124E(4) isblocked by the input device. Transition GUIs 126E(1) and 126E(2) are nowside-by-side on the first display 112(1). Transition GUI 126E(3) showsthat unit 124E(3) of second display 112(2) will be managed for a newfunctionality. The new functionality can be determined based upon thedimensions of the unit and/or be defined by the user. For instance, thedimensions of unit 124E(4) may not lend themselves to presenting contentand may be better suited to other functionalities, such as a touchsensitive tool bar. The touch sensitive tool bar can be generic (e.g.,tied to an operating system of the computing device). Alternatively, thetouch sensitive tool bar could relate to a specific application. Forinstance, GUI 126E(1) could be dedicated to presenting content of anapplication, such as a word processing application, for example. GUI126E(3) could present the controls for the application on the touchsensitive tool bar. Thus, more display area of first unit 124E(1) couldbe dedicated to presenting content at an aspect ratio that lends itselfto content presentation and display area of the third unit 124E(3) canbe used for the control aspects of the application in an aspect ratiothat lends itself to tool bars.

FIG. 1F shows a subsequent point where the user slid the input device104 up the second display 112(2) against the first display 112(1). Unit124F(3) is now blocked by the input device and unit 124F(4) of thesecond display is now available to perform a functionality. Thus, unit124F(4) can now include a GUI 126F(4) while unit 124F(3) does not. Inthis case, the functionality may be touch pad functionality tocomplement the input device, for instance. FIGS. 1E and 1F show that anypositioning of the input device 104 can be accommodated utilizingmultiple units. For instance, if the input device was positioned at anintervening position, additional units could be managed above and belowthe input device.

FIGS. 2A-2G shows another system 200 that can include an examplecomputing device 202 and an associated input device 204 that cancommunicate with computing device 202. In this case, the input device204 can be rotatably secured to the computing device by an input hinge205. One or more sensors 222 can provide sensor data relating to theorientation of the input device 204 to the computing device. In oneimplementation, the sensors can be positioned in the hinge itself. Inanother implementation, the sensors 222 can be positioned in the inputdevice 204 and the computing device 202, such as proximate to the inputhinge 205.

Starting at FIG. 2A, the input device 204 is positioned against thesecond portion 208 on the opposite side from the second display 212(2)(e.g., input device is in a storage position). The first display 212(1)is being managed as a single unit 224A(1). First GUI 226A(1) can bepresented on first unit 224A(1). The second display 212(2) is beingmanaged as a single unit 224A(2). Second GUI 226A(2) can be presented onsecond unit 224A(2).

FIG. 2B shows the input device 204 rotated 90 degrees from theorientation of FIG. 2A. At this point, the first and second units224B(1) and 224B(2) remain unchanged from FIG. 2A.

FIG. 2C shows an additional 90 degrees of rotation of the input device204 from the orientation of FIG. 2B. This may be a working orientation,where the user positions the second portion 206 and the input device 204on a work surface and uses the input device to control the computingdevice 202. The first and second units 224C(1) and 224C(2) remainunchanged from FIG. 2B.

FIG. 2D shows an additional 10 degrees of rotation of the input device204 from the orientation of FIG. 2C (190 degrees of rotation relative toFIG. 2A). At this point, computing device 202 can predict that the userwill continue to rotate the input device and that the input device willvisually and/or physically block some of second display 212(2). As such,units 224D(1) and 224D(2) can be changed as shown by GUIs 226D(1) and226D(2). In this example, unit 224D(1) is narrowed from right to leftand unit 224D(2) is extended up onto the vacated area of first display212(1). This is visually represented by transition GUIs 226D(1) and226D(2).

FIG. 2E shows the input device 204 rotated to the 270-degreeorientation. The first unit 224E(1) as visualized by transition GUI226E(1) is further narrowed and second unit 224E(2) continues to fillthe occupied area as represented by transition GUI 226E(2). Further, athird unit 224E(3) is introduced on the upper left portion of seconddisplay 212(2) as evidenced by transition GUI 226E(3). Thus, FIGS. 2Dand 2E show the user the changes to the displays to compensate for thepresence of the input device 204 on the second portion 208 before suchoccurrence actually happens. Thus, the user can see what is changing andhow it is changing.

FIG. 2F shows the input device 204 rotated 360 degrees from theorientation of FIG. 2A and now contacting the second display 212(2).Units 224F(1) and 224F(2) as visualized by GUIs 226F(1) and 226F(2) arearranged side-by-side on the first display 212(1). A third unit 224F(3)visualized by GUI 226F(3) covers areas of the second display that arenot blocked by the input device. The shape of the third unit may lenditself to specific functions. For instance, the long narrow shape mayfacilitate a toolbar functionality for either or both of GUIs 226F(1)and 226F(2) better than associating the third unit with anotherapplication. The transition GUIs of FIGS. 2D and 2E allow the user to beimmediately ready to use the computing device as configured in FIG. 2Frather than the user having to pause to figure out how the computingdevice was reconfigured. Thus, the user can immediately start readingthe content of GUIs 226F(1) and/or 226F(2) and/or using the input device204.

FIGS. 3A-3D collectively show another scenario where system 300 cancreate visual indications for the user as the configuration of thecomputing device changes.

FIG. 3A shows computing device 302 in a ‘notebook’ orientation with thesecond portion 308 positioned on a horizontal surface (HS) and the firstportion 306 oriented about 90-100 degrees from the second portion. Inthis case, input device 304 is positioned in front of, but separatedfrom, the second portion on the horizontal surface. The computing devicecan employ sensors 322. In this case, the sensors can detect theorientation of the first and second portions in absolute terms and/orrelative to one another. For instance, the sensors could be manifest asmicroelectromechanical systems (MEMS) sensors, such as inertialmeasurement units and/or inertial navigation systems, among others.

In this case, the first display 312(1) is being managed as a single unit324A(1) with a single GUI 326A(1). Similarly, second display 312(2) isbeing managed as a single unit 324A(2) with a single GUI 326A(2). Notethat in this case, text of the GUIs 326A is arranged horizontally. Inthis configuration, the horizontal orientation of the text runs parallelto a length of the displays 312 (e.g., parallel to the hinge axis (HA)).

FIG. 3B shows user 128 grasping the first portion 306 to change theconfiguration of the computing device 302.

FIG. 3C shows the user turning the computing device 302 clockwise. Thesensors 322 can detect this rotation. The computing device can make aprediction from the rotation and control the units 324 accordingly.Further, the computing device can provide indications to the user howthe units will be controlled based upon the prediction. For instance,the prediction may be that the user will continue to rotate thecomputing device into an ‘open book’ configuration where the hinge axisis vertical (e.g., analogous to an open book where the spine is verticaland the text is horizontal on pages that are side by side). In thiscase, transition GUIs 326C(1) and 326C(2) show the text remaininghorizontal despite the rotation of the computing device as an indicationof how the units 324C are being managed.

FIG. 3D shows the user's rotation of the computing device 302 completedwith the hinge axis (HA) now vertical and the first and second portions306 and 308 supporting the computing device on the horizontal surface.In this case, the user does not see any sudden flipping of the text onGUIs 326D, instead the transition GUIs provided indications to the userhow the units 324D and the GUIs where being managed during theconfiguration change. Further, in this case, the prediction allowed theGUI orientation to be maintained throughout the rotation despite therotation of the device, thereby further maintaining continuity andpredictability for the user.

In some implementations, there may be a range of relative orientationsbetween the first and second portions 306 and 308 that can stablysupport the computing device 302. For instance, the range might includeangles between 80 degrees and 150 degrees, for instance. At otherangles, the computing device may be prone to tipping over. Recall thatin some implementations, the sensors 322 can detect the orientation ofthe first and second portions and the relative angle between the firstand second portions and the orientations. For instance, the sensor datamay indicate that the computing device is in a vertical open bookorientation (such as in FIG. 3D) and the first and second portions areat an angle of 110 degrees relative to one another. When the computingdevice is in the vertical open book orientation, a sensory warning maybe emitted if the orientation is outside of the stable range. Forinstance, if the user opens the angle to 170 degrees an audible warningmay be emitted that the user should reduce the angle so that thecomputing device does not fall over.

FIGS. 3A-3D show how the computing device can be seamlessly transitionedfrom the displays positioned over and under (e.g., FIG. 3A) toside-by-side (e.g., FIG. 3D) as desired by the user. In either case, theinput device can augment the functionality of the computing device sothat all of the display area can be managed for content presentation asdesired by the user.

FIG. 4 shows a system 400 that can accomplish display managementconcepts. For purposes of explanation, system 400 can include variouscomputing device 402, such as computing device 402(1)-402(4). Computingdevice 402(1) is similar to computing device 102, 202, and/or 302introduced above that has two displays. Computing device 402(2) islaptop computing device with a single display. Computing device 402(3)is a smart phone type device. Computing device 402(4) is a server typecomputer. Computing devices 402 can communicate via one or more networks(represented by lightning bolts 404). In some cases, parentheticals areutilized after a reference number to distinguish like elements. Use ofthe reference number without the associated parenthetical is generic tothe element.

FIG. 4 shows two device configurations 410 that can be employed bydevices 402. Individual devices 402 can employ either of configurations410(1) or 410(2), or an alternate configuration. (Due to spaceconstraints on the drawing page, one instance of each configuration isillustrated rather than illustrating the device configurations relativeto each device 402). Briefly, device configuration 410(1) represents anoperating system (OS) centric configuration. Configuration 410(2)represents a system on a chip (SOC) configuration. Configuration 410(1)is organized into one or more applications 412, operating system 414,and hardware 416. Configuration 410(2) is organized into sharedresources 418, dedicated resources 420, and an interface 422 therebetween.

In either configuration 410, the device 402 can include storage/memory424, a processor 426, and/or a unit manager 428. In some cases, the unitmanager can include a configuration prediction module 430.

The unit manager 428 can generate and manage units on one or moredisplays of the computing device 402. The unit manager can decide howmany units to employ on the displays, the dimensions of the units,and/or the function of the units. The unit manager can utilize variousparameters as input to make these decisions. For instance, the unitmanager can utilize various parameters about the configuration of thecomputing device. In some cases, the configuration prediction module 430can analyze the parameters to predict a future configuration of thecomputing device. The unit manager 428 can compute how to manage thedisplays for the future configuration. The unit manager can generatetransition GUIs to indicate to the user how the displays will be managedso the user is not surprised and/or confused by the changes.

In some configurations, each of computing devices 402 can have aninstance of the unit manager 428. In other cases, a remote unit managermay determine how to manage the computing device's displays. Forinstance, computing device 402(4) could run a unit manager that receivessensed parameters from computing device 402(3), determines how to managethe display of computing device 402(3), and sends the display managementinformation to computing device 402(3).

The term “device,” “computer,” or “computing device” as used herein canmean any type of device that has some amount of processing capabilityand/or storage capability. Processing capability can be provided by oneor more processors that can execute data in the form ofcomputer-readable instructions to provide a functionality. Data, such ascomputer-readable instructions and/or user-related data, can be storedon storage, such as storage that can be internal or external to thedevice. The storage can include any one or more of volatile ornon-volatile memory, hard drives, flash storage devices, and/or opticalstorage devices (e.g., CDs, DVDs, etc.), remote storage (e.g.,cloud-based storage), among others. As used herein, the term“computer-readable media” can include signals. In contrast, the term“computer-readable storage media” excludes signals. Computer-readablestorage media includes “computer-readable storage devices.” Examples ofcomputer-readable storage devices include volatile storage media, suchas RAM, and non-volatile storage media, such as hard drives, opticaldiscs, and/or flash memory, among others.

Examples of computing devices 402 can include traditional computingdevices, such as personal computers, desktop computers, servers,notebook computers, cell phones, smart phones, personal digitalassistants, pad type computers, mobile computers, smart devices etc.and/or any of a myriad of ever-evolving or yet to be developed types ofcomputing devices.

As mentioned above, configuration 410(2) can be thought of as a systemon a chip (SOC) type design. In such a case, functionality provided bythe computing device can be integrated on a single SOC or multiplecoupled SOCs. One or more processors 426 can be configured to coordinatewith shared resources 418, such as memory/storage 424, etc., and/or oneor more dedicated resources 420, such as hardware blocks configured toperform certain specific functionality. Thus, the term “processor” asused herein can also refer to central processing units (CPUs), graphicalprocessing units (GPUs), field programmable gate arrays (FPGAs),controllers, microcontrollers, processor cores, and/or other types ofprocessing devices.

Generally, any of the functions described herein can be implementedusing software, firmware, hardware (e.g., fixed-logic circuitry), or acombination of these implementations. The term “component” as usedherein generally represents software, firmware, hardware, whole devicesor networks, or a combination thereof. In the case of a softwareimplementation, for instance, these may represent program code thatperforms specified tasks when executed on a processor (e.g., CPU orCPUs). The program code can be stored in one or more computer-readablememory devices, such as computer-readable storage media. The featuresand techniques of the component are platform-independent, meaning thatthey may be implemented on a variety of commercial computing platformshaving a variety of processing configurations.

FIG. 5 is a block diagram of an example implementation of unit manager428. The unit manager 428 can include a GUI host visual tree (alsoreferred to as a GUI host) 502 that can include or reference other GUIhost visual trees 504 for any number of GUI controls for different typesof computing devices, such as 102, 202, 302 of FIGS. 1-3. In someimplementations, the GUI host visual tree 502 can include a GUI controlroot visual 506 that can include Windows.UI.Composition and/or rootExtensible Application Markup Language (XAML) code, for example. The GUIcontrol root visual 506 can declaratively or imperatively generatevarious elements of a unit (e.g., units 124, 224, and/or 324 introducedabove starting with FIG. 1A). For instance, when considering a unit, theGUI control root visual 506 can distinguish unit content 508 from unitsetting 510. The unit setting, sometimes referred to as chrome, tends tobe positioned around the content. The unit setting can be specific to anapplication (app centric 514), such as an application tool bar and/orgeneric 516, such as desktop background, and/or tool bars, taskbars,icons, etc. The unit manager 428 can also incorporate XAML code forgenerating visuals that are running outside of a process such ascomponent applications and top-level applications.

The generic setting 516 can relate to the desktop background and caninclude any suitable image, any number of links or shortcuts to locallystored files, links to directories, and the like. Taskbars can include alink to a digital assistant, a task view illustrating open applications,a set of icons corresponding to applications being executed, and variousicons corresponding to applications and hardware features that areenabled each time a device receives power.

In one example, the unit manager 428 can configure unit sets 520 basedat least in part on input from the prediction module 430 and/or on alist of applications (412, FIG. 4) being executed on the computingdevice (e.g., running appslist 518). The unit sets 520 can include oneor more units (124, FIG. 1A, 224, FIG. 2A, 324, FIG. 3A) for thecomputing device at a specific instance in time. The list ofapplications 518 can indicate a number of applications for which units124 may be managed with associated GUIs (FIG. 1A, 126, 226, FIG. 2A,326, FIG. 3A).

The prediction module 430 can analyze various parameters 522 todetermine the configuration of the computing device at that instant andto predict a future configuration. The parameters 522 can be obtainedfrom and/or relate to input device 104, display 112, sensor 122, and/orother sources 524. For instance, the prediction module 430 can utilizesensor information to determine that the input device is moving towardthe computing device and is likely to be positioned upon the device in amanner that blocks an area of one of the displays 112.

The unit manager 428 can utilize this prediction to define that area asa unit and to manage that unit consistent with the predicted blockage(e.g., don't plan to present an application on the blocked unit becausethe user won't be able to see it). The unit manager can utilizeparameters, the number and/or type of applications that are running, thesize, shape, and/or locations of the units, and/or the location and/orrelative movement of the input device, among others, to compute how tomanage the units.

For instance, the unit manager 428 may determine that the long andnarrow shape of third unit 124E(3) in FIG. 1E may not lend itself tocontent presentation. However, such a long and narrow shape may lenditself for presentation of a tool bar. Thus, unit manager 428 may managesuch a space as a generic tool bar (e.g., allows the user to interactwith the operating system). Alternatively, the unit manager could managethe space as a toolbar associated with another unit, such as unit124E(2). For example, all of unit 124E(2) could be managed forpresenting content associated with an application and unit 124E(3) couldbe used to present the toolbar for the application. As such, the displayarea is better used than is possible in traditional scenarios. Forexample, unit 124E(2) may have an aspect ratio that is preferable forcontent presentation and more display area in unit 124E(2) can bededicated to presenting content, because the toolbar is moved to unit124E(3), which is less desirable for content presentation and wouldotherwise be ‘wasted space’ or ‘under utilized space.’

The unit manager 428 can compute the unit sets 520 based at least inpart on the parameters 522 described above. As mentioned, there may be aone-to-one relationship between units and applications, such as unit124(1) and application 412(1). Alternatively, multiple units can beassociated with an application, such as units 124(2) and 124(3)associated with application 412(2). In some examples one unit is on onedisplay and the other unit is on another display, but they could be onthe same display. Further, units can be associated with the operatingsystem 414, such as unit 124(N) (where ‘N’ indicates that any number ofunits can be employed) associated with operating system 414, such as todisplay a tool bar, function as a touch pad, and/or display operatingsystem content.

As mentioned above, the unit manager 428 can generate transition GUIs(see for example GUIs 126B and 126C of FIGS. 2B and 2C) that can helpthe user understand changes that are being made to the units. Thetransition GUIs may be full featured GUIs (e.g., include all of thedetails and/or features of the original GUI (see GUIs 126A of FIG. 1A)and the updated GUI (see GUIs 126F of FIG. 1F). Alternatively, thetransition GUIs may be simplified GUIs. For instance, the transitionGUIs may maintain the basic appearance of the original and updated GUIswithout the details and/or functionality. For example, the transitionGUIs may have a lower resolution than the original and/or updated GUIs.In another example, the user may not be able to interact with thetransition GUI, such as typing content during the transition.

In some implementations, the unit manager 428 can manage the displays asa set of dynamically variable units. The unit manager can vary the size,aspect ratio, location, and/or function of individual units based uponpresent and/or predicted future conditions of the displays. The unitmanager can utilize a set of private application programming interfaces(APIs) to manage the units. These private APIs can allow the unitmanager to facilitate interactions between applications, the operatingsystem and the units.

FIG. 6 illustrates a flowchart of a display control technique or method600. At block 602, the method can manage a display as a unit. The methodcan manage a single display or multiple displays. Each display can bemanaged as one or more units.

At block 604, the method can identify a change in a condition associatedwith the display. In one case, the change in condition could be that aninput device or other object is going to block an area of the display.In other cases, the change in condition can be a change in orientationof the device. For instance, the user may be rotating the device from alandscape orientation to a portrait orientation or vice versa, amongothers.

At block 606, the method can alter at least one of a location, aspectratio, and/or size of the unit based on the condition. Someimplementations can enhance the user experience by providing transitionsthat are intended to help the user understand the alterations that arebeing performed. For instance, transition GUIs can be presented on theunits that visualize the changes in a manner that the user canunderstand rather than the display suddenly switching from one visualconfiguration to a completely different visual configuration.

The described methods can be performed by the systems and/or elementsdescribed above and/or below, and/or by other display management devicesand/or systems.

The order in which the methods are described is not intended to beconstrued as a limitation, and any number of the described acts can becombined in any order to implement the method, or an alternate method.Furthermore, the method can be implemented in any suitable hardware,software, firmware, or combination thereof, such that a device canimplement the method. In one case, the method is stored on one or morecomputer-readable storage medium/media as a set of instructions (e.g.,computer-readable instructions or computer-executable instructions) suchthat execution by a processor of a computing device causes the computingdevice to perform the method.

The present computing device display management concepts can be utilizedwith any type of computing devices and/or associated input devices, suchas but not limited to notebook computers, smart phones, wearable smartdevices, tablets, and/or other types of existing, developing, and/or yetto be developed devices.

Various methods of manufacture, assembly, and/or use for these devicesand associated input devices are contemplated beyond those shown aboverelative to FIGS. 1A-6.

Although techniques, methods, devices, systems, etc., pertaining todisplay management are described in language specific to structuralfeatures and/or methodological acts, it is to be understood that thesubject matter defined in the appended claims is not limited to thespecific features or acts described. Rather, the specific features andacts are disclosed as example forms of implementing the claimed methods,devices, systems, etc.

Various device examples are described above. Additional examples aredescribed below. One example includes a system comprising an inputdevice and a computing device comprising a first portion associated witha first display and that is rotationally coupled to a second portionassociated with a second display, a unit manager configured to present afirst GUI on the first display and a second GUI on the second display,sensors configured to sense a position of the input device relative tothe computing device, and the unit manager configured to utilize thesensed position to predict that the input device is going to physicallyocclude a portion of the second display and further configured tocompute where to present an updated first GUI and an updated second GUIon the first and second displays to avoid the portion and to presenttransition first and second GUIs on the first and second displays beforethe portion is occluded.

Another example can include any of the above and/or below examples wherethe input device comprises additional sensors that interact with thesensors to provide information about a position and direction ofmovement of the input device relative to the second portion

Another example can include any of the above and/or below examples wherethe input device comprises a keyboard, a touch pad, or a gamecontroller.

Another example can include any of the above and/or below examples wherethe input device is as wide as the first and second displays or whereinthe input device is narrower than the first and second displays.

Another example can include any of the above and/or below examples wherethe unit manager comprises a prediction module that utilizes sensor datato determine the sensed position and direction of movement of the inputdevice.

Another example can include any of the above and/or below examples wherethe transition first and second GUIs have a shape and location that liesbetween a shape and location the first and second GUIs and a shape andlocation of the updated first and second GUIs.

Another example can include any of the above and/or below examples wherethe transition first and second GUIs have a lower resolution than theupdated first and second GUIs.

Another example can include any of the above and/or below examples wherethe transition first and second GUIs comprise a video.

Another example can include any of the above and/or below examples wherethe input device is detachable.

Another example includes a computing device comprising a display, a unitmanager configured to manage a unit of display area at a location on thedisplay, sensors configured to sense a position of an input devicerelative to the computing device, and the unit manager configured toutilize the sensed position to predict that the input device is going tophysically occlude a portion of the display and further configured tocompute where to position the unit at another location on the displaythat does not include the portion.

Another example can include any of the above and/or below examples wherethe unit is a rectangle having first dimensions at the location andsecond dimensions at the another location.

Another example can include any of the above and/or below examples wherethe first dimensions and the second dimensions are the same.

Another example can include any of the above and/or below examples wherethe unit manager is further configured to generate a transition GUI thatis located between the location and the another location.

Another example can include any of the above and/or below examples wherethe transition GUI has dimensions that are between the first dimensionsand the second dimensions.

Another example can include any of the above and/or below examples wherethe transition GUI comprises a series of transition GUIs.

Another example can include any of the above and/or below examples wherethe transition GUI comprises a transition GUI video.

Another example includes a device comprising a display and storage. Thedevice also comprises a processor configured to execute computerreadable instructions stored on the storage, comprising managing thedisplay as a unit, identifying a change in a condition associated withthe display, and altering at least one of a location, aspect ratio, orsize of the unit based on the condition.

Another example can include any of the above and/or below examples wherethe processor performs the altering before the change in the conditionoccurs.

Another example can include any of the above and/or below examples wherethe display comprises multiple displays and wherein the alteringcomprises moving the unit from a first of the multiple displays to asecond of the multiple displays.

Another example can include any of the above and/or below examples wherethe unit comprises a first unit on the first display and a second uniton the second display and wherein the altering comprises resizing thefirst unit on the first display and moving the second unit from thesecond display to the first display.

Another example can include any of the above and/or below examples wherethe altering comprises generating transition GUIs that illustratechanges to the location, aspect ratio, or size of the unit.

Another example can include any of the above and/or below examples wherethe identifying comprises predicting the change prior to the changeoccurring.

Another example can include any of the above and/or below examples wherethe change relates to a change in visible display area.

1. A system, comprising: an input device; and, a computing devicecomprising: a first portion associated with a first display and that isrotationally coupled to a second portion associated with a seconddisplay; sensors configured to sense a current position of the inputdevice relative to the computing device; and, a display unit managerconfigured to present a first GUI on the first display and a second GUIon the second display, utilize the current position of the input deviceto predict a future position of the input device that will physicallyocclude a portion of the second display, compute where to present anupdated first GUI on the first display and an updated second GUI on thesecond display to avoid the portion when the input device reaches thefuture position, and present a transition first GUI on the first displayand a transition second GUI on the second display before the inputdevice reaches the future position.
 2. The system of claim 1, whereinthe input device comprises additional sensors that interact with thesensors to provide information about the current position and adirection of movement of the input device relative to the secondportion.
 3. The system of claim 1, wherein the input device comprises akeyboard, a touch pad, or a game controller.
 4. The system of claim 1,wherein the input device is as wide as the first and second displays orwherein the input device is narrower than the first and second displays.5. The system of claim 1, wherein the display unit manager comprises aprediction module that utilizes sensor data to determine the currentposition and a direction of movement of the input device.
 6. The systemof claim 1, wherein the transition first and second GUIs have a shapeand location that lies between a shape and location the first and secondGUIs and a shape and location of the updated first and second GUIs. 7.The system of claim 1, wherein the transition first and second GUIs havea lower resolution than the updated first and second GUIs.
 8. The systemof claim 1, wherein the transition first and second GUIs comprise avideo.
 9. The system of claim 1, wherein the input device is detachable.10. A computing device comprising: a display; a display unit managerconfigured to manage a unit of display area at a location on thedisplay; sensors configured to sense a current position of an inputdevice relative to the computing device; and, the display unit managerconfigured to utilize the current position to predict a future positionof the input device that will physically occlude a portion of thedisplay, compute where to position the unit at another location on thedisplay that does not include the portion, and present a transition GUIon the display before the input device reaches the future position. 11.The computing device of claim 10, wherein the unit is a rectangle havingfirst dimensions at the location and second dimensions at the anotherlocation.
 12. The computing device of claim 11, wherein the firstdimensions and the second dimensions are the same.
 13. The computingdevice of claim 12, wherein the transition GUI is located between thelocation and the another location.
 14. The computing device of claim 13,wherein the transition GUI has dimensions that are between the firstdimensions and the second dimensions.
 15. The computing device of claim13, wherein the transition GUI comprises a series of transition GUIs.16. The computing device of claim 15, wherein the transition GUIcomprises a transition GUI video.
 17. A device, comprising: a display;storage; and, computer readable instructions stored on the storage that,when executed, cause a processor to perform operations comprising:managing the display as a unit, identifying a change in a currentcondition associated with the display, predicting a future conditionassociated with the display based at least on the change, computing afuture alteration of at least one of a location, aspect ratio, or sizeof the unit based at least on the future condition, and presenting atransition alteration of the at least one of the location, aspect ratio,or size of the unit before the future condition occurs.
 18. The deviceof claim 17, wherein the processor performs the computing the futurealteration before the future condition occurs.
 19. The device of claim17, wherein the display comprises a first display and a second display,and wherein the future alteration comprises moving the unit from a firstdisplay to a second display.
 20. The device of claim 19, wherein theunit comprises a first unit on the first display and a second unit onthe second display and wherein the future alteration comprises resizingthe first unit on the first display and moving the second unit from thesecond display to the first display.